release: 0.4.2 #86
Merged
release: 0.4.2 #86
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Contributor
Author
|
🧪 Testing To try out this version of the SDK, run: Expires at: Wed, 14 Jan 2026 09:42:55 GMT |
stainless-app
bot
force-pushed
the
release-please--branches--main--changes--next
branch
from
7bfed68 to
d621125
Compare
Added permissions for id-token in publish job.
stainless-app
bot
force-pushed
the
release-please--branches--main--changes--next
branch
from
d621125 to
16a2996
Compare
easyCZ
approved these changes
Dec 15, 2025
stainless-app
bot
deleted the
release-please--branches--main--changes--next
branch
Contributor
Author
|
🤖 Release is at https://github.com/gitpod-io/gitpod-sdk-python/releases/tag/v0.4.2 🌻 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Automated Release PR
0.4.2 (2025-12-15)
Full Changelog: v0.4.1...v0.4.2
Bug Fixes
Chores
This pull request is managed by Stainless's GitHub App.
The semver version number is based on included commit messages. Alternatively, you can manually set the version number in the title of this pull request.
For a better experience, it is recommended to use either rebase-merge or squash-merge when merging this pull request.
🔗 Stainless website
📚 Read the docs
🙋 Reach out for help or questions